Skip to content

Fix badge for CI build on the default branch - #17901

Merged
nvborisenko merged 1 commit into
SeleniumHQ:trunkfrom
nvborisenko:readme-fix-badge
Aug 11, 2026
Merged

Fix badge for CI build on the default branch#17901
nvborisenko merged 1 commit into
SeleniumHQ:trunkfrom
nvborisenko:readme-fix-badge

Conversation

@nvborisenko

@nvborisenko nvborisenko commented Aug 11, 2026

Copy link
Copy Markdown
Member

This pull request makes a minor update to the README.md file, specifically updating the CI badge image URLs to include the ?event=push query parameter. This ensures that the badges reflect the status of push events.

  • Updated the CI and CI - RBE badge URLs in README.md to include ?event=push, so the badges display the status of push events.

🔗 Related Issues

I eventually see red badge in README while CI workflow actually passed in the default branch.

image image

Why is it red?

💥 What does this PR do?

Filter CI workflow status to be triggered by push event.

🔄 Types of changes

  • Cleanup (formatting, renaming)

@qodo-code-review

Copy link
Copy Markdown
Contributor

PR Summary by Qodo

Fix GitHub Actions CI badges to show push status on default branch

📝 Documentation 🕐 Less than 5 minutes

Grey Divider

AI Description

• Update CI badge URLs to filter status by push events
• Prevent README badges from showing non-push (e.g., PR) failures on default branch
High-Level Assessment

The chosen approach is appropriate: GitHub Actions badge URLs support the ?event=push filter, which aligns the badge with the default-branch push workflow status and avoids misleading badge states from other event types.

Files changed (1) +2 / -2

Documentation (1) +2 / -2
README.mdFilter CI badges to push event status +2/-2

Filter CI badges to push event status

• Updates the CI and CI - RBE GitHub Actions badge image URLs to include '?event=push'. This makes the README badges reflect push-event results (e.g., default-branch pushes) rather than other workflow event types that can cause confusing red badges.

README.md

@qodo-code-review

Copy link
Copy Markdown
Contributor

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can group findings by type and pick your Finding display, from Minimal to Full

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@cgoldberg cgoldberg left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cool.. I had no idea the badges accepted args

@nvborisenko

Copy link
Copy Markdown
Member Author

I verified, it shows green. Let's keep eyes. Merging.

@nvborisenko
nvborisenko merged commit d05f029 into SeleniumHQ:trunk Aug 11, 2026
20 checks passed
@nvborisenko
nvborisenko deleted the readme-fix-badge branch August 11, 2026 19:21
@nvborisenko

nvborisenko commented Aug 11, 2026

Copy link
Copy Markdown
Member Author

Passing (previous commit)... While my commit is still in progress.

@nvborisenko

Copy link
Copy Markdown
Member Author

"CI" workflow is only one from many others. Currently our badge looks at "CI".

Seems it would be better that badge shows status of the latest commit in default branch. Not a priority, if somebody knows - nice.

This was referenced Aug 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants